IBIS Macromodel Task Group

Meeting date: 28 nov 2006

Members (asterisk for those attending):
* Arpad Muranyi, Intel Corp.
  Barry Katz, SiSoft
* Bob Ross, Teraspeed Consulting Group
* Doug White, Cisco Systems
* Hemant Shah, Cadence Design Systems
* Ian Dodd, Mentor Graphics
  Joe Abler, IBM
  John Angulo
  John Shields, Mentor Graphics
  Ken Willis, Cadence Design Systems
* Kumar, Cadence Design Systems
* Lance Wang, Cadence Design Systems
* Michael Mirmak, Intel Corp.
* Mike LaBonte, Cisco Systems
  Paul Fernando, NCSU
* Randy Wolff, Micron Technology
  Richard Ward, Texas Instruments
  Sanjeev Gupta, Agilent
  Shangli Wu, Cadence
  Todd Westerhoff, Cisco Systems
* Walter Katz, SiSoft
  Vuk Borich, Agilent
  Vikas Gupta, Xilinx

-------------
Review of ARs:

- Mirmak: Who has permission to access VHDL spec P1076C?
  Has anyone tried?
  Lance needs access info. Must be an IEEE member.
  May be available under IEEE Explorer
  Requires a paid account.

- Mike update macro library documentation
  Will do it this week

- Ian get specifics on pole/zero approach
  - Nothing yet
  - Multiple ways to represent channel characteristics.
  - Impule response may not be flexible enough.
  - We are looking for ways to make the current proposal more specific.
  - Will current API proposal work?

- Cadence will start a BIRD
  - In internal review.
  - Will be sent next week.

- Todd dig up material on public domain HSPICE syntax
  - No report.

-------------
New Discussion:

AR: Mirmak send spreadsheet on convolution operators

Pole/zero approach
- Kumar: would only apply in Init()
- Ian: impulse response is truncated in time
- What length of response is needed? Should set criteria.
- Walter: Long impulse response makes convolution go to hell.
  - Agree with Ian that proposed structure is not sufficient.
  - Could not design current channel project with Cadence API.
- Time to do convolution proportional to square of impulse response.
- API can support multiple formats, freq. vs. time domain
- Ian: EESof would probably prefer S-param

- Hemant: API must be extended to allow pole/zero tables

AR: Hemant share details with Ian before proposing BIRD

Arpad: IBIS 4.2 spec is vague about parameter "assignments"
- provides param names only, is optional
- external model must have defaults built-in
- parameter GUI needs to know type and current value
- Arpad: would be better to have this in IBIS
- Could call the same model definition with different params to create different model instances.

- Walter: typ, min, max should be typ, slow, fast
- Mirmak: no presets, would rather have "knobs" to turn. Ex. SPICE
- Need to give legal range, which may be a set of values. Also units.
  - Ian proposed this at the DAC summit.
- Arpad: declaration should remain in AMS model

- How to handle units and scaling?
- should be consistent with other parts of IBIS

AR: Walter send units ideas to Arpad

-------------

Next meeting: Tuesday 04 Dec 2006 12:00pm PT